I have the problem of 2 different DOORS DBs and I need some object information (attribute values) of an object in one DB in the other DB. The objects are linked with external links on both sides (in and outlink as a combination), so the reference is clear. Is there a way to get this information with OLE automatisation? Is it possible to get a specific DOORS instance? E.g. with the oleGetAutoObject or the oleCreateAutoObject command.
Does somebody now a documentation of the supported OLE methods in DOORS?
Any help would be very appreciated.
ibmmm
ibmmm - Tue May 27 05:16:37 EDT 2014 |
Re: OLE automatisation to other DOORS DB This is possible. The main consideration is that the oleGetAutoObject call will always return the instance of DOORS that was started FIRST. There is some more backgroud information on this topic in the following thread: Tony |
Re: OLE automatisation to other DOORS DB Tony_Goodman - Tue May 27 08:51:59 EDT 2014 This is possible. The main consideration is that the oleGetAutoObject call will always return the instance of DOORS that was started FIRST. There is some more backgroud information on this topic in the following thread: Tony Thank you for your answer.
Is it possible to follow a external link to another DOORS DB to get information from the linked item like a status value? I would like to do this via OLE automatisation. ibmmm |
Re: OLE automatisation to other DOORS DB ibmmm - Wed May 28 05:40:09 EDT 2014 Thank you for your answer.
Is it possible to follow a external link to another DOORS DB to get information from the linked item like a status value? I would like to do this via OLE automatisation. ibmmm No. You will not be able to follow an external link and work in the other client. You will have two separate DOORS clients, one for each database and they cannot work together. You would need to get the url from the external link on client A and then use OLE Automation to Control client B, locating the object using information extracted from the url. This could get very messy. A better solution might be to record the Module paths/IDs and Object IDs in an attribute on client A, the use OLE automation, or even better import an archive from the other database? Tony |
Re: OLE automatisation to other DOORS DB Tony_Goodman - Wed May 28 08:32:38 EDT 2014 No. You will not be able to follow an external link and work in the other client. You will have two separate DOORS clients, one for each database and they cannot work together. You would need to get the url from the external link on client A and then use OLE Automation to Control client B, locating the object using information extracted from the url. This could get very messy. A better solution might be to record the Module paths/IDs and Object IDs in an attribute on client A, the use OLE automation, or even better import an archive from the other database? Tony Thank you very much for your Help. Importing an archive is not a solution because there should be an up to date status several times a week. The paths and IDs are known on the evaluating side - at least within the external links. So it sounds that this solution could work. I will try it next week to set up this communication. ibmmm |